Skip to content

Conversation

@assagman
Copy link
Owner

Summary

  • Add repository.url field to package.json
  • Fixes npm publish provenance verification error (E422)

Problem

npm OIDC trusted publishing with --provenance validates that package.json repository URL matches the GitHub Actions source repository. Publishing failed with:

Error verifying sigstore provenance bundle: Failed to validate repository information: 
package.json: "repository.url" is "", expected to match "https://github.com/assagman/opencode-toolbox"

Fix

Added the required repository field to package.json:

"repository": {
  "type": "git",
  "url": "https://github.com/assagman/opencode-toolbox"
}

Copilot AI review requested due to automatic review settings January 15, 2026 22:05
@gemini-code-assist
Copy link

Summary of Changes

Hello @assagman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical issue encountered during npm OIDC trusted publishing. By introducing the repository.url field into the package.json file, it ensures that the package's declared repository URL aligns with the GitHub Actions source, thereby satisfying the provenance verification requirements and allowing successful package publication.

Highlights

  • Configuration Update: The repository.url field has been added to the package.json file.
  • Error Resolution: This change resolves an E422 npm publish provenance verification error that occurred during OIDC trusted publishing.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@assagman assagman merged commit a1c9554 into main Jan 15, 2026
5 checks passed
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly adds the repository field to package.json to resolve an npm provenance verification error. The change is straightforward and effective. I've added one suggestion to align the repository URL with common conventions for better clarity.

"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/assagman/opencode-toolbox"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While the provided URL works, it's a common convention to use the full Git URL ending with .git. This makes it explicit that it's a cloneable repository URL and aligns with examples in the npm documentation.

Suggested change
"url": "https://github.com/assagman/opencode-toolbox"
"url": "https://github.com/assagman/opencode-toolbox.git"

@assagman assagman deleted the fix/repository-url-for-npm-provenance branch January 15, 2026 22:06
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds the required repository.url field to package.json to fix npm OIDC trusted publishing provenance verification errors. When publishing with the --provenance flag, npm validates that the package.json repository URL matches the GitHub Actions source repository, and this field was previously missing.

Changes:

  • Added repository field with type "git" and URL pointing to the GitHub repository

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions github-actions bot mentioned this pull request Jan 15, 2026
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants